This activity is optional depending on the agreed scope and approach in Focus And direction. If in the Focus and Direction it has been agreed that the Application Landscape is in scope this activity will be executed. In case of a feasibility study or software package selection the Application Landscape will be in scope. The level of granularity is determined and agreed on in the Approach.

If this activity is performed after the Information Usage activity it is mainly concerned with identifying the Application Landscape that is in scope. This is done by mapping the data used by the processes on the data interaction of the applications. The deliverable will be the As-Is Application Landscape.

If the client has limited documentation of the processes this activity can be the starting point of the As-Is Understanding. The Existing Application Landscape is the starting point for identifying the As-Is Information, As-Is Process and As-Is Business.

The application mapping can be useful for spotting duplicate functionality and data. The mapping is done by mapping the data used by the processes on the data interaction of the applications.

Requirements regarding Application Landscape are recognized, collected and documented only if they were not already captures in the Business Requirements Catalogue. This would be the Business requirements Catalogue of the customer and is part of the Consolidated and Validated Intake Report.